feat(usd): price every trade and fee at the time it happened - #133

…trade

The read side of Twigpine#133. The all-time volume, the fee totals, each token's "Total
volume" and the all-time Volume sort now read the stored trade-time values
(each trade and fee at its own hour), instead of quote volume at today's price.
Production was backfilled on 2026-11-10: $16,601,255 stored, against the
$11.7M the old method showed.

- trade-time-usd.ts (pure): tradeTimeUsd = the stored sum plus the raw amount
  with no stored value at today's price. That second part covers registry
  stocks, community pairs and unlisted tokens traded before the live capture
  started (no price history: 4,711 of 133k trades), so the totals stay complete.
  missingNow decides "partial": only that part can be missing a price.
- queries.ts:
  - the list SELECT joins each launch's unpriced volume once (one grouped read
    on the usd-IS-NULL partial index)
  - shape() computes volume_usd from it and no longer passes the stored columns
    through
  - the all-time Volume sort ranks by the same figure
  - getLaunchTotals sums the stored values plus the unpriced parts; fees to
    recipients = collected - burned, both in trade-time USD
  - 1h/24h volume stays quote volume at today's price, where every trade is
    priced live anyway
- LaunchMechanism: the tooltips say how the figures are valued (each at the hour
  it happened; stock and community-pair trades before Nov 10, 2026 at today's
  rate), not "valued at current rates".
- Tests: trade-time-usd.test.ts. The totals fixture (price-source) moves to the
  new model, plus a case where a trade priced at $3,100 stays $3,100 at an ETH
  price of $2,500. The source checks for the partial rule, the select's aliases
  (the new `u` join) and the hero tooltip are updated; the db mock knows the new
  totals query.

Not changed: CollectPanel's per-token fee figures and the live tape (recent
trades, at today's price), points scoring (this season).

Verified on a throwaway Postgres 16: the real migration, a fixture backfilled by
the real apply SQL, then the real getLaunch / listLaunchesPage(volume, all) /
getLaunchTotals at ETH = $2,500:
- ETH $4,789.65, USDC $100, GITLAWB $18,893.73
- an unlisted quote null
- an ETH trade from before the backfill range at today's price ($2,500)
- sort CGIT > AETH > EOLD > BUSDC > DUNL
- total $26,283.38, not partial
- no stored column leaks into the API rows
tsc and lint clean; npm test 1408 (1397 pass, 11 skipped, 0 fail).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

From a strict review of af4e6e5..133fabd (Twigpine#133, Twigpine#136):

- Community pairs are never stored (usdLedger.capturable). A pair priced from an
  outside pool can be pushed for a minute, and a captured price stayed in the
  totals for good. A suspended or delisted pair must show no USD, which a stored
  value defeated. Their trades keep usd NULL and count at the pair's price now,
  which follows its listing status. The backfill (apply) clears pair values
  captured since Twigpine#133 and drops their ledger rows.
- A launch row whose volume is partly unpriced while its quote has no price
  right now shows its quote amount (launchVolumeUsd: null) instead of a smaller
  dollar figure that looked complete.
- The receipt path (applyLaunchTx, the user is waiting) no longer captures live
  prices: a capture could wait on Coinbase and Chainlink. Those trades take the
  hour's price the poller captured, or the heal pass prices them.
- Heal pass (usdLedger.healUnpricedUsd), every 5 minutes per chain after a sync:
  - prices the last 3 days' trades and quote-side fees with no USD whose hour now
    has a price, and adds them to the launch totals in the same statement
  - skips pairs and re-tests usd IS NULL inside the UPDATE, so two machines
    change each row and each total once
- Backfill apply is ONE transaction under the rebuild-launch-totals locks: pair
  cleanup, pricing and the totals recompute commit together. No reader sees rows
  priced but not yet summed, and a failure changes nothing. The dry run counts
  pairs as unpriced and stays write-free.
- The lists probe one launch at a time (LATERAL u on the new partial index
  bb_launch_swaps_usd_missing_token_idx) instead of aggregating every unpriced
  trade per request. The totals' unpriced-fee read gets
  bb_launch_fee_events_usd_missing_idx.
- scripts/rebuild-launch-totals.sql recomputes the USD totals too and reports
  USD drift before and after.
- Wording: the tooltip and the partial note describe what has no recorded value.
  The backfill retries network errors and timeouts, not only 429/5xx.

Deferred, not risky: the pairs pages and the token fee panel still use today's
price; the volume sort mixes units during an ETH price outage (pre-existing);
per-hour source labels; poolMaps / quoteUsdNow duplication.

Verified on a throwaway Postgres 16 with the real migration (3 partial indexes
built):
- two concurrent heal passes priced the missed trade and fee once (AETH $2,000 →
  $6,200, not $10,400; fee $21); a rerun and a throttled run changed nothing; the
  pair stayed NULL
- the dry run reported pairs as unpriced and changed nothing
- apply (1 BEGIN / 1 COMMIT) cleared the old pair value and its ledger rows and
  left AETH at $6,200
- the repair script ran with 0 USD drift
- the real reads: AETH $6,200, the pair row null (quote amount), sort ok, totals
  $6,200 and partial
tsc and lint clean; npm test 1410 (1399 pass, 11 skipped, 0 fail).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>